Amazon's data model — FBA and MFN fulfillment, two-week settlement payouts, ASIN-to-SKU mapping, fee reconciliation — doesn't map cleanly to NetSuite without deliberate configuration. Entech builds Celigo integrations that handle the full Amazon–NetSuite data flow, including the accounting and reconciliation pieces that generic connector setups typically skip.
Talk to an integration expert →The core outcome: Amazon orders reach NetSuite automatically, inventory stays accurate on your listings, and Amazon settlements reconcile to your books without a manual step.
Both Merchant Fulfilled and Fulfilled by Amazon orders pull from Seller Central and create NetSuite Sales Orders. MFN orders need to be shipped from your warehouse with tracking pushed back to Amazon. FBA orders are already fulfilled by Amazon — the Sales Order records the sale, but fulfillment confirmation comes from Amazon, not your team. One integration, two different downstream workflows.
Available quantity in NetSuite pushes to your MFN listing inventory. FBA inventory lives in Amazon's warehouses — Amazon controls what the listing shows, but FBA stock levels can sync back to NetSuite for internal reporting.
Once an MFN order ships in NetSuite, tracking number and carrier data push to Amazon, closing the order and triggering Amazon's customer notification. Late confirmations affect seller performance metrics.
Amazon returns trigger credit memos, customer refunds, and inventory adjustments in NetSuite depending on whether stock returns to your warehouse (MFN) or is restocked by Amazon (FBA). Custom handling logic is almost always needed.
Amazon pays out every two weeks — net amounts after referral fees, FBA fees, advertising costs, and refund deductions. Mapping settlements to NetSuite requires a deliberate choice between per-order reconciliation and summary journal entries. Either needs to be designed, not defaulted.
Pricing can sync from NetSuite to Amazon listings via a maintained ASIN-to-NetSuite-Item mapping table. SKU is the linking field — but only if it has been maintained consistently across both systems.
The Celigo Amazon–NetSuite Integration App covers the standard Seller Central order-to-cash flow well. These are the cases that require more than standard configuration.
Most sellers use a mix. These fulfillment models have fundamentally different data flows — FBA needs fee reconciliation and Amazon-side inventory reporting; MFN needs outbound fulfillment tracking and warehouse inventory sync. One integration needs to handle both correctly without conflating the two workflows.
This is the piece most Amazon–NetSuite integrations underinvest in. Amazon's settlements bundle orders, refunds, fees, and adjustments into a net payout. How this maps to NetSuite determines whether your Amazon channel P&L is meaningful or misleading. It requires design decisions, not defaults.
SKU is the field that links Amazon and NetSuite. Many sellers have years of SKU inconsistencies — trailing spaces, case mismatches, legacy formats — that surface immediately when the integration first runs. A consistency audit before go-live prevents a cascade of unmatched records.
Each Amazon marketplace — US, CA, UK, EU — has its own order feed, inventory, settlement currency, and tax rules. Multi-marketplace multiplies the configuration scope considerably. Establish marketplace count during scoping, not mid-build.
Vendor Central (selling directly to Amazon as a first-party supplier) uses EDI-based flows — 850 purchase orders, 856 advance ship notices, 810 invoices. Seller Central is what the Celigo app covers. If you operate in both, that is two separate integration builds.
FBA fees, referral fees, and advertising costs appear in settlements and need to be allocated correctly in NetSuite for accurate channel P&L. How your finance team wants fees categorised needs to be agreed before configuration begins, not after.
We use Celigo's Amazon–NetSuite Integration App as the foundation. Standard Seller Central setups are efficient. Multi-marketplace, Vendor Central, or complex settlement reconciliation gets custom flows.
FBA vs MFN scope, marketplace count, settlement reconciliation approach. SKU consistency audit. Vendor Central involvement. Fee allocation agreed with finance.
Celigo flows, field mappings, custom logic. Settlement reconciliation, multi-marketplace routing, return handling.
Real Amazon order data across both fulfillment types. Settlement reconciliation against actual payout reports. Partial refunds, FBA returns, cancelled orders, multi-currency.
Client validates end-to-end. Phased cutover with monitoring. 4–6 weeks for single-marketplace. 8–12 for multi-marketplace or Vendor Central.
Amazon Seller Central access, NetSuite admin access, a finance contact for settlement decisions, and a SKU list from both systems for the consistency check.
Entech has built Amazon–NetSuite integrations on Celigo for distribution and ecommerce clients running mixed FBA and MFN models. On the NetSuite side, our work spans standard Sales Order flows through custom multi-subsidiary implementations — including the settlement reconciliation and fee accounting that connector-only setups typically leave to the client.
Whether you're setting this up for the first time, replacing a connector that's not handling settlements correctly, or expanding to additional marketplaces — tell us your setup before you commit to an approach.